Enhance KYC sharing documentation#123
Merged
andregoncalvesdev merged 1 commit intoJun 17, 2026
Merged
Conversation
|
🚀 Preview has been deployed.
|
andregoncalvesdev
requested changes
Jun 1, 2026
59cf44e to
69e2268
Compare
69e2268 to
6332943
Compare
andregoncalvesdev
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Reframes the KYC sharing documentation to clearly position shareable tokens as the recommended approach and KYC sharing API as the alternative for partners that don't use Sumsub.
Changes in docs/kyc-sharing.md:
:::tip"Recommended approach" admonition on that section.### User experiencesubsection describing the end-to-end flow (KYC onboarding screen → Sumsub SDK initiation → liveness check → optional additional KYC based on the user's country) with an embedded video walkthrough.:::info"Alternative approach" admonition on the API section and strengthened the compliance note — partners using the API must be approved by Compliance to be authoritative for the shared scopes.Related issues